Skip to content

Hide internal chat tool messages#50

Merged
nttylock merged 1 commit into
mainfrom
codex/customer-chat-guard-20260521
May 21, 2026
Merged

Hide internal chat tool messages#50
nttylock merged 1 commit into
mainfrom
codex/customer-chat-guard-20260521

Conversation

@nttylock

Copy link
Copy Markdown
Member

Summary

  • filter internal reasoning/tool/MCP messages out of customer chat history
  • hide live operate-card rows on chat pages as a short-term guard

Scope

Validation

  • git diff --check
  • changed files limited to console/src/pages/Chat/sessionApi/index.ts and console/src/styles/layout.css
  • synced files match private origin/main for these two paths

@nttylock nttylock merged commit 9595be4 into main May 21, 2026
7 checks passed
@nttylock nttylock deleted the codex/customer-chat-guard-20260521 branch May 21, 2026 12:51

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e4f0ee5590

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +74 to +75
.page-content-chat .adclaw-operate-card {
display: none !important;

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Keep approval cards visible on chat pages

This selector hides every adclaw-operate-card, not just reasoning/tool trace rows, so approval UIs are also suppressed; when an MCP/tool flow emits an approval request card, users cannot see or act on it and the run can stall waiting for input. This affects any environment where approval-gated tool execution is enabled.

Useful? React with 👍 / 👎.

.join("\n");
}

const INTERNAL_OUTPUT_TYPES = new Set([

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Filter all internal runtime event message types

The internal-type filter is incomplete: it excludes some tool/runtime events but leaves other non-chat event types unfiltered, so shouldRenderOutputMessage can still surface internal execution traffic in history when those message types appear. To match the stated behavior, expand this set (or switch to an explicit allowlist of user-visible message types).

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant